Re: View definition and schema search path bug or expected behaviour? - Mailing list pgsql-general

From Chris Bartlett
Subject Re: View definition and schema search path bug or expected behaviour?
Date
Msg-id p06240807cc365f416396@[192.168.200.4]
Whole thread Raw
In response to Re: View definition and schema search path bug or expected behaviour?  (Adrian Klaver <adrian.klaver@gmail.com>)
Responses Re: View definition and schema search path bug or expected behaviour?  (Adrian Klaver <adrian.klaver@gmail.com>)
List pgsql-general
At 7:37 PM -0700 25/7/12, Adrian Klaver wrote:
>I am guessing if you do  show search_path; from psql you will see
>that the public schema is before the bob schema. The SELECT for the
>unqualified people table in CREATE VIEW bob.people_view will find
>public.people first in that case.

I don't think that's it:

show search_path
-> "$user",public

select SESSION_USER
-> bob

 From the docs:
"The value for search_path must be a comma-separated list of schema
names. If one of the list items is the special value $user, then the
schema having the name returned by SESSION_USER is substituted, if
there is such a schema. (If not, $user is ignored.)"

Also:
select * from people
-> returns records from bob.people

pgsql-general by date:

Previous
From: Adrian Klaver
Date:
Subject: Re: View definition and schema search path bug or expected behaviour?
Next
From: Adrian Klaver
Date:
Subject: Re: View definition and schema search path bug or expected behaviour?